Automated bundling of content

ABSTRACT

Non-limiting examples describe automated bundling of content on behalf of a user by an application/service. As an example, a bundle of content may be a bundle of emails created on behalf of a user by an email service. Email data associated with a user account of an email service may be accessed. The email data may be evaluated by applying a bundle generation model that that evaluates the emails for bundling associations. An exemplary bundle generation model may evaluate the email data based on: user signal data from actions pertaining to categorization of specific emails, content and metadata corresponding with the email data, and server side metric analysis of activity corresponding with the user account. A bundle of emails may be automatically generated based on an evaluation result from applying the bundle generation model. The bundle of emails may be transmitted for display in a mailbox of the user account.

BACKGROUND

Currently, the only mechanisms available to a user to group together like content is through folder creation or through the creation of a label. In one instance, traditional email clients allow a user to create a folder and move content into the folder. However, this folder is outside the inbox, thus demoting the importance of said messages. Further, the folder structure is everlasting and remains a fixture in a navigational pane of an email client, which can clog up a mailbox of a user. Folder structures can also complicate a user interface of an email client, especially when users access an email client through a mobile device, which has limited display space. Furthermore, limitations with folder structures exist when there are other users that content is to be shared with. With folder structures, the other users are required to manually access a folder and do not receive automatic content updates. In alternative instances a user can create a label for management of content. However, labels work like folders and have the same issues as described above. Labels are not ephemeral, have sharing limitations and have the potential to clog up the user interface and mailbox history of an email client. Moreover, in either the folder or label instances, traditional email clients are not configured to automatically bundle content on behalf of a user.

As such, examples of the present application are directed to the general technical environment related to improving operation of an email service, where processing efficiency and usability are improved, among technical benefits.

SUMMARY

Non-limiting examples describe automated bundling of content on behalf of a user by an application/service. As an example, a bundle of content may be a bundle of emails created on behalf of a user by an email service. Email data associated with a user account of an email service may be accessed. The email data may be evaluated by applying a bundle generation model that that evaluates the emails for bundling associations. An exemplary bundle generation model may evaluate the email data based on: user signal data from actions pertaining to categorization of specific emails, content and metadata corresponding with the email data, and server side metric analysis of activity corresponding with the user account. A bundle of emails may be automatically generated based on an evaluation result from applying the bundle generation model. The bundle of emails may be transmitted for display in a mailbox of the user account.

This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter. Additional aspects, features, and/or advantages of examples will be set forth in part in the description which follows and, in part, will be apparent from the description, or may be learned by practice of the disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

Non-limiting and non-exhaustive examples are described with reference to the following figures.

FIG. 1 illustrates an exemplary system implementable on one or more computing devices on which aspects of the present disclosure may be practiced.

FIG. 2 is an exemplary method related to automated bundling of content on behalf of a user with which aspects of the present disclosure may be practiced.

FIGS. 3A-3B provide user interface views illustrating user interface examples for managing bundling of emails in an email service, with which aspects of the present disclosure may be practiced.

FIG. 4 is a block diagram illustrating an example of a computing device with which aspects of the present disclosure may be practiced.

FIGS. 5A and 5B are simplified block diagrams of a mobile computing device with which aspects of the present disclosure may be practiced.

FIG. 6 is a simplified block diagram of a distributed computing system in which aspects of the present disclosure may be practiced.

DETAILED DESCRIPTION

Non-limiting examples of the present disclosure describe automatic bundling of content on behalf of a user. As an example, an exemplary bundle of content may be a bundle of emails associated with an email service. Exemplary bundles of content provide an alternative solution to folder/label solutions, where bundles of content are ephemeral in nature and can be presented inline with other content (e.g. email content) of an application/service (e.g. email service). While examples herein relate to automatic bundling of content on behalf of a user, it is to be understood that examples described herein may extend to any aspect for management of bundled content including but not limited to: user-creation of a bundle of content, sharing of bundled content, enhanced search and filtering functionality for content (including bundled content) and generation of rich content previews for bundles of content. Other aspects related to management of bundled content may be provided in related co-pending applications.

FIG. 1 illustrates an exemplary system 100 implementable on one or more computing devices on which aspects of the present disclosure may be practiced. System 100 may be an exemplary system for execution of an email service with which aspects of the present disclosure may be practiced. Components of system 100 may be hardware components or software implemented on and/or executed by hardware components. In examples, system 100 may include any of hardware components (e.g., ASIC, other devices used to execute/run an OS, and software components (e.g., applications, application programming interfaces, modules, virtual machines, runtime libraries) running on hardware. In one example, an exemplary system 100 may provide an environment for software components to run, obey constraints set for operating, and makes use of resources or facilities of the systems/processing devices, where components may be software (e.g., application, program, module) running on one or more processing devices. For instance, software (e.g., applications, operational instructions, modules) may be executed on a processing device such as a computer, mobile device (e.g., smartphone/phone, tablet) and/or any other type of electronic devices. As an example of a processing device operating environment, refer to operating environments of FIGS. 4-6. One or more components of system 100 may be configured to execute any of the processing operations described in at least method 200 described in the description of FIG. 2. In other examples, the components of systems disclosed herein may be spread across multiple devices. Exemplary system 100 comprises email service components 106 that further comprise: an auto-bundling component 108 and a mailbox management component 110.

One or more data stores/storages or other memory may be associated with system 100. For example, a component of system 100 may have one or more data storage(s) 112 (described below) associated therewith. Data associated with a component of system 100 may be stored thereon as well as processing operations/instructions executed by a component of system 100. Furthermore, it is presented that application components of system 100 may interface with other application services. Application services may be provided as platform resources referenced in the foregoing. Application services may be any resource that may extend functionality of one or more components of system 100. Application services may include but are not limited to: personal intelligent assistant services, web search services, e-mail applications, word processing applications, spreadsheet applications, presentation applications, notes applications, calendaring applications, device management services, address book services, informational services, line-of-business (LOB) management services, customer relationship management (CRM) services, debugging services, accounting services, payroll services and services and/or websites that are hosted or controlled by third parties, among other examples. Application services may further include other websites and/or applications hosted by third parties such as social media websites; photo sharing websites; video and music streaming websites; search engine websites; sports, news or entertainment websites, and the like. Application services may further provide analytics, data compilation and/or storage service, etc., in association with components of system 100.

System 100 may comprise one or more storage(s) 112 that may store data associated with operation of one or more components of system 100. In examples, storage(s) 112 may interface with other components of system 100. Data associated with any component of system 100 may be stored in storage(s) 112, where components may be connected to storage(s) 112 over a distributed network including cloud computing platforms and infrastructure services. Exemplary storage(s) 112 may be any of a first-party source, a second-party source, and a third-party source. Storage(s) 112 are any physical or virtual memory space. Storage(s) 112 may store any data for processing operations performed by components of system 100, retained data from processing operations, stored programs, code or application programming interfaces (APIs), training data, links to resources internal and external to system 100 and knowledge data among other examples. Furthermore, in examples, components of system 100 may utilize knowledge data in processing by components of system 100. Knowledge may be used by one or more components of system 100 to improve processing of any of the email service components 106 where knowledge data can be obtained from resources internal or external to system 100. In examples, knowledge data may be maintained in storage(s) 112 or retrieved from one or more resources external to system 100 by knowledge fetch operation.

In FIG. 1, processing device 102 may be any device comprising at least one processor and at least one memory/storage. Examples of processing device 102 may include but are not limited to: processing devices such as desktop computers, servers, phones, tablets, phablets, slates, laptops, watches, and any other collection of electrical components such as devices having one or more processors or circuits. In one example processing device 102 may be a device of a user that is executing applications/services such as an exemplary email service (e.g. email client). An example of an email service is Outlook®. In examples, processing device 102 may communicate with the email service components 106 via a network 104. In one aspect, network 104 is a distributed computing network, such as the Internet. Email service components 106 may also communicate with application services via the network 104. Processing device 102 may be a device as described in the description of FIGS. 4-6. In some examples, processing device 102 may comprise multiple connected devices. Processing device 102 is an example of a user computing device.

The processing device 102 may execute processing operations that include an ability to access an application/service through a user account. In one example, processing device 102 may connect an authenticated user to an exemplary application/service that stores user data for one or more users of the application/service. For example, a user, utilizing processing device 102, may access an email service, where the email service may authenticate a user account of the user. The email service may access a mailbox management component 110 (of the email service components 106) to provide, to the processing device 102, a representation of a mailbox (of the email service) that is associated with the user account of the user.

An exemplary storage application/service may provide a user of processing device 102 with access to data stored in an exemplary data center. In one example, processing device 102 may be connected with storage(s) 112 via a distributed network, which may provide users with access to user data. One or more tenant resources (e.g. Tenant Resource A, Tenant Resource B, Tenant Resource C, etc.) may be associated with processing device 102. A tenant resource may be a user account associated with a processing device and/or distributed network service. Data associated with a tenant resource may be stored on storage(s) 112, where a tenant account can be utilized to access stored data by processing device 102 and/or other processing devices. Email service components 106 are components configured to execute processing operations to enable creation, sharing and management of a bundle of emails within an exemplary email service that is executing on client computing device 102. While examples described herein reference bundling of emails in an email service, it is to be understood that examples described herein are not limited to bundling of emails (of an email service) and may extend to any type of data bundling that can be used to replace folders/labels for bundling data for a service. The email service components 106 are executed by one or more computing devices. An exemplary computing device may comprise one or more processors and memory, among other components. Examples of computing devices are provided in the description of at least FIGS. 4-6. As referenced above, the email service components 106 comprise: an auto-bundling component 108 and a mailbox management component 110.

The auto-bundling component 108 is configured to manage auto-creation of bundles on behalf of a user. In addition to enabling bundle creation by a user, an exemplary email service may be configured to bundle content for the user as well as provide suggestions for bundling of content to a user. For example, an email service may be configured to parse email data, evaluate the email data to identify similar content and group the content in bundles on behalf of the user. This not only helps organize a mailbox of a user but also enables the user to initiate bulk actions simultaneously on multiple emails. For instance, a user may receive multiple messages from an advertising service, which the user may consider spam. Evaluation of user signal data pertaining to previous user actions as well as content/metadata associated with specific emails can identify the nature of an email (e.g. classify/categorize the email) and take action on behalf of the user. In some instances, the auto-bundling component 108 is configured to provide suggestions/recommendations to a user, which can be confirmed to trigger automated action with respect to content of a user mailbox. User interface examples of an email service pertaining to auto-bundling are provided in at least FIGS. 3A and 3B.

Custom bundles (e.g. bundles of emails) are a light-weight mechanism for managing associations between content (e.g. emails where a bundle of emails may be created). A bundle can be defined as an automatic of manually set grouping of like items. As an example, a bundle may be created to group two or more email messages of an email service, creating a bundle of emails. An exemplary bundle of emails may comprise a grouping of at least two separate email threads. The bundle of emails may further comprise an exemplary tag, providing an association to an entity type tagging structure. An exemplary entity type tagging structure can be utilized to classify emails of an email service including bundled emails. Data associated with the entity type tagging structure (including an exemplary tag) can be used to assist with searching and filtering of email data including bundles of emails.

An exemplary tag is further used to associate email messages and content of the bundle (e.g. bundle of emails). The tag associates an email message (and/or other content) with one or more additional email (and/or other content). In one example, an exemplary tag is a hashtag. However, tags are not limited to such a form. Created tags become entity values that can be used to efficiently associate emails of a bundle. Tags further become entity data that can be used to prioritize searching and retrieval of created bundles. In some instances, tags may remain associated with a bundle even when a message is separated from a bundle. This may assist users with being able to quickly relocate an email during a subsequent search. In alternative examples, an email that was previously associated with a bundle and later removed may not retain an association to an exemplary tag.

A bundle of emails is tagged with the bundle name/tag ID as part of an entity type tagging infrastructure. In one example, an entity type tagging infrastructure may be used for the assignment and management of tags associated with bundles of emails. That is, an entity type tagging structure may be generated for specific emails included in a bundle of emails. The entity type tagging structure may comprise a plurality of fields that are configured by developers, where data of the entity type tagging infrastructure can be utilized for management of content associated with a bundle including searching and filtering of bundles of content and sharing of bundled content. Attributes and fields associated with an exemplary entity type tagging infrastructure may vary based on the type of email content. In further examples, an entity type tagging infrastructure may be used for classification of any type of emails including emails not included in a bundle of emails as data from an entity type tagging infrastructure may be utilized to increase accuracy in classifying emails as a specific type or category. An exemplary categorization for a bundle of emails may be useful for back-end processing performed by the email service including: analysis of the bundle of emails (including content of the bundle of emails), generation of a representation of an exemplary mailbox, generation of recommendations/suggestions for a user, telemetry analysis for the email service and/or other associated applications/services, and other aspects of management of bundled content (e.g. sharing, searching/filtering, generation of rich content previews, etc.) among other examples. Examples of data fields that may be included in an exemplary entity type tagging infrastructure comprise but are not limited to: context fields pertaining to specific data of an email, tag/hashtag fields, email type fields, category fields, entity data fields, data source fields, date/timestamp information, hyperlink data fields, domain information fields, formatting/arrangement fields, confidence scores pertaining to classification and specific attributes of an email, data pertaining to specific email content and user triage action history with respect to specific messages (e.g. emails) and/or a category/type for the specific message, among other examples.

An exemplary bundle is contextually relevant and presented inline with other emails of a user mailbox. An email service is configured to create bundles of content on behalf of a user based on meaningful categories for the user/groups of users. This is a better solution than folders, labels or setting of email rules because a created bundle is ephemeral in nature. Bookmarked links such as folders/labels are not required to be created within a navigational pane of a user interface of an email service. Further, bundled content is automatically updated and intelligently managed by an email service, where bundled content can be automatically updated based on changes to message content associated with a user mailbox. If the topic item becomes irrelevant, a bundle would drop off (e.g. de-prioritize), but the bundle structure would still remain intact allowing for a bundle to be found later without requiring a physical link to be created and managed within a navigational pane of an email service (i.e. as with folders/labels). If a bundle receives a new message or update that may be relevant to a user (e.g. meeting appointment, tracking of shipment, notification, etc.), the bundle would be prioritized in a mailbox of a user. Notably, once a bundle is created in an email service, subsequent email messages from bundled message threads may result in update to the created bundle, where a user would not have to go looking for individual messages/message threads.

Additionally, an exemplary bundle of content may inherit all (or some) of the triage actions and behaviors associated with a single message. That is, an email service is configured to enable a user to execute bulk actions with respect to a bundle of content (e.g. bundle of emails). For instance, a user can delete a bundle of emails without being required to go in and execute actions on specific emails.

Furthermore, an exemplary bundle is configured to manage associations with other application/services such as platform resources that may comprise a suite of different applications. For instance, a user may have a calendared appoint setup with the dentist of the user. Notifications and alerts associated with such content may presented to the user in conjunction with a created bundle. When bundled content is shared, such notifications may also be provided to other users of the shared bundle. As an example, a schedule appointment (associated with a shared bundle) may also appear on a calendar of a shared user.

In order to ensure that the shared bundle participants can later get back to content they had previously classified to be part of a bundle, the emails within that bundle are stamped with a property (e.g. tag) that identifies these emails as pertaining to this topic or category. For example, all emails that the user adds to a shared “vacation” bundle are tagged using the hashtag “#vacation”. If the user later searches for “vacation” this is translated to a search for all “#vacation” emails such that these emails appear higher in the relevance ranking than those that simply have the keyword “vacation.” In further examples, a user mailbox (of an email service) can be organized according to categories that comprise auto-bundled content. As a visual example, refer to FIG. 3A.

The auto-bundling component 108 is configured to evaluate content associated with an email service and automatically generate bundles of content (or suggestions for bundling content) on behalf of a user/group of users. In one example, there are many emails (e.g. commercial emails) that a user does not pay attention to. In such an example, the auto-bundling component 112 is configured to auto-bundle emails on behalf of the user, for example, so a user can execute bulk action with respect to a bundle of emails. An exemplary bundle of content may inherit all of the triage actions and behaviors associated with a single message.

As another example, if a user were to receive a batch of meeting invites, the auto-bundling component 108 is configured to auto-bundle the unread invites automatically, allowing the user to see them all together. This is extremely useful in instances where the user receives many invites (over a period time) and may have forgotten to respond. Rather than having to go look for the invites, the auto-bundling component 108 can collect and present the invites for the user. The user can then respond to the meeting invites in bulk or one-by-one basis.

As a further example, the auto-bundling component 108 may be configured to recognize that a user gets email updates hourly from a specific auto-mailer. The auto-bundling component 108 is configured to automatically bundle these emails on the user's behalf to help unclutter the user's inbox, for example, without requiring the user to take action or request assistance with managing such emails.

As suggested by the above examples, the auto-bundling component 108 is configured to tailor/personalize bundles of emails for the user. The auto-bundling component 108 automatically creates/personalizes bundles for the user based on the specifics of their inbox rather than based upon generic categories that pertain to most users. In doing so, the auto-bundling component 108 is configured to apply a bundle generation model that evaluates the emails for bundling associations that may be most appropriate for the user. An exemplary bundle generation model may be a machine learning model that is trained to make auto-bundling determinations on behalf of the user, for example, by evaluating one or more of: user signal data associated with a user account of an email service, content and metadata associated with specific emails and server side metrics for activity that corresponds with the user account, among other examples. An exemplary bundle generation model is configured to interface with an exemplary email service as well as other applications/services to collect and obtain data used for making auto-bundling determinations and suggestions.

In making an auto-bundling determination, the bundle generation model is configured to evaluate client-side signals that pertain to categorization of specific emails by the user/user account. An exemplary email service may be configured to provide categories (e.g. newsletters, promotions, travel, etc.) for different email messages, where the categories may be auto-created by the email service or user-created. The bundle generation model is configured to collect and evaluate signal data that pertains to the user actively categorizing email content within a mailbox of a user account. As an example, user signal data, may be collected and evaluated, that pertains to created bundles of emails, which are used for categorization of email content.

The bundle generation model is configured to evaluate any type of user actions related to categorization of email messages to gain an understanding as to how the user prefers to organize its mailbox. Examples of user categorization actions analyzed by the bundle generation model include but are not limited to: adding/removing content from a category/bundle, re-classifying content, creating new bundles for content and deleting bundles, among other examples. For instance, if the user moves a technology-based email from a technology news category/bundle to newsletter category/bundle, the bundle generation model will learn that for this user, the categorization was not correct and it will correct itself in the future. Such information is helpful in making auto-bundling determinations for similar email content.

In addition to taking queues from the user's actions specific to the client UI for an email service, the bundle generation model also learns above the user based upon server side metric analysis of activity corresponding with a user account. As an example, server side metric analysis may evaluate signal data pertaining to activity/usage of an email account. Data collected and evaluated in an exemplary service side metric analysis may include but is not limited to any of: sender domains for emails received by the user account, telemetry data corresponding with user access actions for specific emails, user rules set in association with the user account, telemetry data from cross-application usage by the user account for a suite of platform applications, time stamp evaluation, date range evaluation and importance/flag evaluation, among other examples.

For example, server side metric analysis may identify that a user receives multiple messages from GitHub® a day and has created a rule that moves these messages into a specific folder. Further evaluation may identify that the user checks and triages this folder multiple times a day. Such information can be useful in determining whether to auto-bundle such content allowing the user to see these emails more easily, take bulk actions with respect to this created bundle (e.g. delete all emails) and not require the user to have to create rules for managing such email content. Likewise, server side metric analysis may identify that the user constantly performs delete or mark as read actions without opening the emails on a certain set of sender domains. The bundle generation model may be configured to make an auto-bundling determination to group such emails together thus allowing the user to better perform bulk triage actions on the bundle.

Furthermore, the bundle generation model may further evaluate content and/or metadata corresponding with specific email data in generating an auto-bundling determination or suggestion. Evaluation of specific content of an email may be useful in identifying the nature of an email and whether the email would be of interest to the user. An evaluation of content/metadata of an email may be used in coordination with other collected signal data (e.g. user signal data and analysis of server side metrics) to assist in generating an auto-bundling determination. Examples of content and/or metadata that may be evaluated by the bundle generation model include but is not limited to: sender, recipients, subject, attachments, text, signature blocks, keywords, and a category/classification for the email, among other examples.

In other examples, the bundle generation model can further evaluate user signal data to generate suggestions for bundling of content. In addition to user signal data, server side metric analysis and email content/metadata may also factor into generation of an exemplary bundling suggestions. Suggestions generated by the bundle generation model may comprise suggestions for creation of new bundles (e.g. auto-creation of bundles) as well as suggestions for adding new message content to created bundles. For instance, if a user creates a new bundle for “Tech News” articles by moving a TechCrunch® email on top of a Verge® email, the bundle generation model will learn that each of these emails belongs to a category of “Tech News” and can send all future mails of these kinds to the created bundle. In such an example, a suggestion may be generated for future automatic bundling of content. Further, evaluation by the bundle generation model may also identify other emails that pertain to this category and suggest to the user that they be added to the “Tech News” bundle.

The mailbox management component 110 is a component configured to manage email data associated with a user account of an email service and provide a representation of a mailbox (of the email service) that is associated with the user account of the user. The mailbox management component 110 may retrieve email data associated with the user account and generate a representation of a mailbox for the user. An exemplary representation of the mailbox may be provided through an email service (e.g. executing on a processing device such as processing device 102). Generation of a representation of a mailbox of a user is known to one skilled in the art. Moreover, the mailbox management component 110 may interface with the bundle sharing component 108 to enable the auto-bundling component 108 to access email data (associated with a user account) as well as email data associated with other user accounts for sharing of bundled content. Data associated with executing processing operations for automated bundling of content may be shared between components of an email service including the auto-bundling component 108, the mailbox management component 110 and other components for the management of bundled content. For instance, data associated with a created bundle of emails may be shared with the mailbox management component 110 to include a bundle of emails in a generated representation of a mailbox of the email service.

FIG. 2 is an exemplary method 200 related to automated bundling of content on behalf of a user with which aspects of the present disclosure may be practiced. As an example, method 200 may be executed by an exemplary processing device and/or system such as those shown in FIGS. 4-6. In examples, method 200 may execute on a device comprising at least one processor configured to store and execute operations, programs or instructions. Operations performed in method 200 may correspond to operations executed by a system and/or service that execute computer programs, application programming interfaces (APIs), neural networks or machine-learning processing, among other examples. As an example, processing operations executed in method 200 may be performed by one or more hardware components. In another example, processing operations executed in method 200 may be performed by one or more software components. In some examples, processing operations described in method 200 may be executed by one or more applications/services associated with a web service that has access to a plurality of application/services, devices, knowledge resources, etc. Processing operations described in method 200 may be implemented by one or more components connected over a distributed network, for example, as described in system 100 (of FIG. 1).

Method 200 begins at processing operation 202, where email data associated with a user account of an email service may be accessed. Exemplary email data may pertain to emails for a user account of the email service. Email data may be accessed (processing operation 202) with user consent in accordance with policies outlined for application/service usage for an email service and/or suite of applications of a specific platform. As an example, email data that is accessed for bundling may pertain to a specific tab classification of a mailbox of a user. In one example, email data that is accessed may be emails that are commercial in nature, where an email service is attempting to assist a user with auto-bundling of content for a user to take bulk action with respect to bundled content.

Flow may proceed to processing operation 204, where accessed email data may be evaluated for bundling associations. Processing operation 204 may comprise applying an exemplary bundle generation model that is configured to make determinations for auto-bundling content and/or generation of suggestions for auto-bundling of content that may be confirmed by a user. Examples of processing executed by an exemplary bundle generation model is described in the description of the auto-bundling component 108 (of FIG. 1). As an example, the bundle generation model may evaluate the email data based on: user signal data from actions pertaining to categorization of specific emails, content and metadata corresponding with the email data, and server side metric analysis of activity corresponding with the user account.

In one example, the user signal data pertains to user actions that correspond with created bundles of emails in the mailbox of the user account. For instance, the user actions may comprise a user action of moving an email from a first created bundle to a second created bundle. A created bundle of emails may be a user-created bundle of emails or an auto-generated bundle of emails that are associated with a specific user account. In one example, a created bundle of emails may comprise: a grouping of two or more emails, a categorization for the grouping of emails and an identification tag associated with the categorization. An exemplary entity type tagging infrastructure may be associated with a created bundle of emails.

The server side metric analysis evaluates data that comprises any of: sender domains for emails received by the user account, telemetry data corresponding with user access actions for specific emails, user rules set in association with the user account and telemetry data from cross-application usage by the user account for a suite of platform applications, among other examples. Additional examples of evaluation of server side metric analysis are provided in the description of the auto-bundling component 108 (of FIG. 1). Examples related to content and metadata of specific email content is also provided in the description of the auto-bundling component 108 (of FIG. 1).

In some examples, evaluation of email data by a bundle generation model may yield a determination to provide an auto-bundling suggestion to a user before automatically bundling content on behalf of the user. In one instance, such a determination may be made based on confidence scoring associated with evaluation of (e.g. confidence score is not high enough to give the email service a clear indication that a user would prefer an auto-bundling association). An exemplary bundle generation model may be configured to have threshold values set for determining when to auto-bundle content and when to provide suggestions to a user. In other instances, an exemplary email service may be configured to simply make auto-bundling suggestions and learn user preferences from corrections made by the user with respect to auto-bundles provided by the email service. In examples where the bundle generation model determines to provide a suggestion for auto-bundling of content, flow may proceed to processing operation 206, where a suggestion for re-organizing created bundles of emails in the mailbox of the user account is generated. Flow may further proceed to processing operation 208, where the suggestion is transmitted/provided to a mailbox of the user account.

In other examples of method 200, a bundle of emails may be automatically generated (processing operation 210) based on an evaluation result from applying the bundle generation model. The generated bundle of emails may be transmitted (processing operation 212) for display in a mailbox of the user account. In further examples, the auto-generated bundle of emails may be displayed (processing operation 214) through a mailbox (e.g. for a user account) of an email service.

An exemplary email service may be further configured to generate (processing operation 216) and transmit/provide (processing operation 218) a notification for automatic bundling of the bundle of emails to a user account. Further description related to auto-bundling notification is provided in the description of the auto-bundling component 108 (of FIG. 1).

FIGS. 3A-3B provide user interface views illustrating user interface examples for managing bundling of emails in an email service, with which aspects of the present disclosure may be practiced. FIGS. 3A and 3B provide user interface examples related to auto-bundling of emails on behalf of a user by an exemplary email service. Automatic bundle generation (as well as automatic suggestion generation for bundling) is described in at least the description of the auto-bundling component 108 of FIG. 1.

FIG. 3A illustrates user interface view 300, which provides a display of a user inbox of an exemplary email service. User interface view 300 provides an example of an auto-generated bundle 302 that was generated by an email service on behalf of a user. As an example, the auto-generated bundle 302 relates to a classification of “newsletters”, where the auto-generated bundle 302 comprises emails 304 that are categorized within the a “newsletters” category, for example, based on an evaluation executed by the auto-bundling component 108 (described in FIG. 1). As described above, auto-bundling of content may be utilized for arranging contents of a mailbox for a user. In some instances, users may provide feedback (e.g. user signal data) that can be used to automatically re-generate bundles/groupings of content for the user.

FIG. 3B illustrates user interface view 310, which provides a display of a user inbox of an exemplary email service. User interface view 310 provides a notification 312 for a bundle of emails 314 that was auto-generated on behalf of a user. An exemplary notification 312 may provide indication to a user that a bundle of emails 314 was created on behalf of the user. An exemplary notification 312 not only alerts a user that a bundle was auto-generated for the user but also enables the user to confirm that the email service was correct in auto-bundling content for the user. Alternative examples of notification 312 may comprise a suggestion for auto-bundling of email content. For example, an email service may provide a suggestion notification indicating an intention to auto-bundle content on behalf of the user, where the user can elect to confirm the auto-bundling of the content.

FIGS. 4-6 and the associated descriptions provide a discussion of a variety of operating environments in which examples of the invention may be practiced. However, the devices and systems illustrated and discussed with respect to FIGS. 4-6 are for purposes of example and illustration and are not limiting of a vast number of computing device configurations that may be utilized for practicing examples of the invention, described herein.

FIG. 4 is a block diagram illustrating physical components of a computing device 402, for example a mobile processing device, with which examples of the present disclosure may be practiced. Among other examples, computing device 402 may be an exemplary computing device configured for execution of an email service as described herein. In a basic configuration, the computing device 402 may include at least one processing unit 404 and a system memory 406. Depending on the configuration and type of computing device, the system memory 406 may comprise, but is not limited to, volatile storage (e.g., random access memory), non-volatile storage (e.g., read-only memory), flash memory, or any combination of such memories. The system memory 406 may include an operating system 407 and one or more program modules 408 suitable for running software programs/modules 420 such as IO manager 424, other utility 426 and application 428. As examples, system memory 406 may store instructions for execution. Other examples of system memory 406 may store data associated with applications. The operating system 407, for example, may be suitable for controlling the operation of the computing device 402. Furthermore, examples of the invention may be practiced in conjunction with a graphics library, other operating systems, or any other application program and is not limited to any particular application or system. This basic configuration is illustrated in FIG. 4 by those components within a dashed line 422. The computing device 402 may have additional features or functionality. For example, the computing device 402 may also include additional data storage devices (removable and/or non-removable) such as, for example, magnetic disks, optical disks, or tape. Such additional storage is illustrated in FIG. 4 by a removable storage device 409 and a non-removable storage device 410.

As stated above, a number of program modules and data files may be stored in the system memory 406. While executing on the processing unit 404, program modules 408 (e.g., Input/Output (I/O) manager 424, other utility 426 and application 428) may perform processes including, but not limited to, one or more of the stages of the operations described throughout this disclosure. Other program modules that may be used in accordance with examples of the present invention may include electronic mail and contacts applications, word processing applications, spreadsheet applications, database applications, slide presentation applications, drawing or computer-aided application programs, photo editing applications, authoring applications, etc.

Furthermore, examples of the invention may be practiced in an electrical circuit comprising discrete electronic elements, packaged or integrated electronic chips containing logic gates, a circuit utilizing a microprocessor, or on a single chip containing electronic elements or microprocessors. For example, examples of the invention may be practiced via a system-on-a-chip (SOC) where each or many of the components illustrated in FIG. 4 may be integrated onto a single integrated circuit. Such an SOC device may include one or more processing units, graphics units, communications units, system virtualization units and various application functionality all of which are integrated (or “burned”) onto the chip substrate as a single integrated circuit. When operating via an SOC, the functionality described herein may be operated via application-specific logic integrated with other components of the computing device 402 on the single integrated circuit (chip). Examples of the present disclosure may also be practiced using other technologies capable of performing logical operations such as, for example, AND, OR, and NOT, including but not limited to mechanical, optical, fluidic, and quantum technologies. In addition, examples of the invention may be practiced within a general purpose computer or in any other circuits or systems.

The computing device 402 may also have one or more input device(s) 412 such as a keyboard, a mouse, a pen, a sound input device, a device for voice input/recognition, a touch input device, etc. The output device(s) 414 such as a display, speakers, a printer, etc. may also be included. The aforementioned devices are examples and others may be used. The computing device 404 may include one or more communication connections 416 allowing communications with other computing devices 418. Examples of suitable communication connections 416 include, but are not limited to, RF transmitter, receiver, and/or transceiver circuitry; universal serial bus (USB), parallel, and/or serial ports.

The term computer readable media as used herein may include computer storage media. Computer storage media may include volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information, such as computer readable instructions, data structures, or program modules. The system memory 406, the removable storage device 409, and the non-removable storage device 410 are all computer storage media examples (i.e., memory storage.) Computer storage media may include RAM, ROM, electrically erasable read-only memory (EEPROM), flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other article of manufacture which can be used to store information and which can be accessed by the computing device 402. Any such computer storage media may be part of the computing device 402. Computer storage media does not include a carrier wave or other propagated or modulated data signal.

Communication media may be embodied by computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and includes any information delivery media. The term “modulated data signal” may describe a signal that has one or more characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media may include wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, radio frequency (RF), infrared, and other wireless media.

FIGS. 5A and 5B illustrate a mobile computing device 500, for example, a mobile telephone, a smart phone, a personal data assistant, a tablet personal computer, a phablet, a slate, a laptop computer, and the like, with which examples of the invention may be practiced. Mobile computing device 500 may be an exemplary computing device configured for execution of an email service as described herein. Application command control may be provided for applications executing on a computing device such as mobile computing device 500. Application command control relates to presentation and control of commands for use with an application through a user interface (UI) or graphical user interface (GUI). In one example, application command controls may be programmed specifically to work with a single application. In other examples, application command controls may be programmed to work across more than one application. With reference to FIG. 5A, one example of a mobile computing device 500 for implementing the examples is illustrated. In a basic configuration, the mobile computing device 500 is a handheld computer having both input elements and output elements. The mobile computing device 500 typically includes a display 505 and one or more input buttons 510 that allow the user to enter information into the mobile computing device 500. The display 505 of the mobile computing device 500 may also function as an input device (e.g., touch screen display). If included, an optional side input element 515 allows further user input. The side input element 515 may be a rotary switch, a button, or any other type of manual input element. In alternative examples, mobile computing device 500 may incorporate more or less input elements. For example, the display 505 may not be a touch screen in some examples. In yet another alternative example, the mobile computing device 500 is a portable phone system, such as a cellular phone. The mobile computing device 500 may also include an optional keypad 535. Optional keypad 535 may be a physical keypad or a “soft” keypad generated on the touch screen display or any other soft input panel (SIP). In various examples, the output elements include the display 505 for showing a GUI, a visual indicator 520 (e.g., a light emitting diode), and/or an audio transducer 525 (e.g., a speaker). In some examples, the mobile computing device 500 incorporates a vibration transducer for providing the user with tactile feedback. In yet another example, the mobile computing device 500 incorporates input and/or output ports, such as an audio input (e.g., a microphone jack), an audio output (e.g., a headphone jack), and a video output (e.g., a HDMI port) for sending signals to or receiving signals from an external device.

FIG. 5B is a block diagram illustrating the architecture of one example of a mobile computing device. That is, the mobile computing device 500 can incorporate a system (i.e., an architecture) 502 to implement some examples. In one examples, the system 502 is implemented as a “smart phone” capable of running one or more applications (e.g., browser, e-mail, calendaring, contact managers, messaging clients, games, and media clients/players). In some examples, the system 502 is integrated as a computing device, such as an integrated personal digital assistant (PDA), tablet and wireless phone.

One or more application programs 566 may be loaded into the memory 562 and run on or in association with the operating system 564. Examples of the application programs include phone dialer programs, e-mail programs, personal information management (PIM) programs, word processing programs, spreadsheet programs, Internet browser programs, messaging programs, and so forth. The system 502 also includes a non-volatile storage area 568 within the memory 562. The non-volatile storage area 568 may be used to store persistent information that should not be lost if the system 502 is powered down. The application programs 566 may use and store information in the non-volatile storage area 568, such as e-mail or other messages used by an e-mail application, and the like. A synchronization application (not shown) also resides on the system 502 and is programmed to interact with a corresponding synchronization application resident on a host computer to keep the information stored in the non-volatile storage area 568 synchronized with corresponding information stored at the host computer. As should be appreciated, other applications may be loaded into the memory 562 and run on the mobile computing device (e.g. system 502) described herein.

The system 502 has a power supply 570, which may be implemented as one or more batteries. The power supply 570 might further include an external power source, such as an AC adapter or a powered docking cradle that supplements or recharges the batteries.

The system 502 may include peripheral device port 530 that performs the function of facilitating connectivity between system 502 and one or more peripheral devices. Transmissions to and from the peripheral device port 530 are conducted under control of the operating system (OS) 564. In other words, communications received by the peripheral device port 530 may be disseminated to the application programs 566 via the operating system 564, and vice versa.

The system 502 may also include a radio interface layer 572 that performs the function of transmitting and receiving radio frequency communications. The radio interface layer 572 facilitates wireless connectivity between the system 502 and the “outside world,” via a communications carrier or service provider. Transmissions to and from the radio interface layer 572 are conducted under control of the operating system 564. In other words, communications received by the radio interface layer 572 may be disseminated to the application programs 566 via the operating system 564, and vice versa.

The visual indicator 520 may be used to provide visual notifications, and/or an audio interface 574 may be used for producing audible notifications via the audio transducer 525 (as described in the description of mobile computing device 500). In the illustrated example, the visual indicator 520 is a light emitting diode (LED) and the audio transducer 525 is a speaker. These devices may be directly coupled to the power supply 570 so that when activated, they remain on for a duration dictated by the notification mechanism even though the processor 560 and other components might shut down for conserving battery power. The LED may be programmed to remain on indefinitely until the user takes action to indicate the powered-on status of the device. The audio interface 574 is used to provide audible signals to and receive audible signals from the user. For example, in addition to being coupled to the audio transducer 525 (shown in FIG. 5A), the audio interface 574 may also be coupled to a microphone to receive audible input, such as to facilitate a telephone conversation. In accordance with examples of the present invention, the microphone may also serve as an audio sensor to facilitate control of notifications, as will be described below. The system 502 may further include a video interface 576 that enables an operation of an on-board camera 530 to record still images, video stream, and the like.

A mobile computing device 500 implementing the system 502 may have additional features or functionality. For example, the mobile computing device 500 may also include additional data storage devices (removable and/or non-removable) such as, magnetic disks, optical disks, or tape. Such additional storage is illustrated in FIG. 5B by the non-volatile storage area 568.

Data/information generated or captured by the mobile computing device 500 and stored via the system 502 may be stored locally on the mobile computing device 500, as described above, or the data may be stored on any number of storage media that may be accessed by the device via the radio 572 or via a wired connection between the mobile computing device 500 and a separate computing device associated with the mobile computing device 500, for example, a server computer in a distributed computing network, such as the Internet. As should be appreciated such data/information may be accessed via the mobile computing device 500 via the radio 572 or via a distributed computing network. Similarly, such data/information may be readily transferred between computing devices for storage and use according to well-known data/information transfer and storage means, including electronic mail and collaborative data/information sharing systems.

FIG. 6 illustrates one example of the architecture of a system for providing an application that reliably accesses target data on a storage system and handles communication failures to one or more client devices, as described above. The system of FIG. 6 may be an exemplary system configured for execution of an email service as described herein. Target data accessed, interacted with, or edited in association with programming modules 408 and/or applications 420 and storage/memory (described in FIG. 4) may be stored in different communication channels or other storage types. For example, various documents may be stored using a directory service 622, a web portal 624, a mailbox service 626, an instant messaging store 628, or a social networking site 630, application 428, IO manager 424, other utility 426, and storage systems may use any of these types of systems or the like for enabling data utilization, as described herein. A server 620 may provide storage system for use by a client operating on general computing device 402 and mobile device(s) 500 through network 615. By way of example, network 615 may comprise the Internet or any other type of local or wide area network, and a client node may be implemented for connecting to network 615. Examples of a client node comprise but are not limited to: a computing device 402 embodied in a personal computer, a tablet computing device, and/or by a mobile computing device 500 (e.g., mobile processing device). As an example, a client node may connect to the network 615 using a wireless network connection (e.g. WiFi connection, Bluetooth, etc.). However, examples described herein may also extend to connecting to network 615 via a hardwire connection. Any of these examples of the client computing device 402 or 500 may obtain content from the store 616.

Reference has been made throughout this specification to “one example” or “an example,” meaning that a particular described feature, structure, or characteristic is included in at least one example. Thus, usage of such phrases may refer to more than just one example. Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more examples.

One skilled in the relevant art may recognize, however, that the examples may be practiced without one or more of the specific details, or with other methods, resources, materials, etc. In other instances, well known structures, resources, or operations have not been shown or described in detail merely to observe obscuring aspects of the examples.

While sample examples and applications have been illustrated and described, it is to be understood that the examples are not limited to the precise configuration and resources described above. Various modifications, changes, and variations apparent to those skilled in the art may be made in the arrangement, operation, and details of the methods and systems disclosed herein without departing from the scope of the claimed examples. 

What is claimed is:
 1. A method comprising: accessing email data associated with a user account of an email service; evaluating the email data by applying a bundle generation model that evaluates the emails for bundling associations based on: user signal data from actions pertaining to categorization of specific emails, content and metadata corresponding with the email data, and server side metric analysis of activity corresponding with the user account; automatically bundling two or more emails into a bundle of emails based on an evaluation result from application of the bundle generation model; and transmitting the bundle of emails for display in a mailbox of the user account.
 2. The method of claim 1, wherein the user signal data pertains to user actions that correspond with created bundles of emails in the mailbox of the user account, and wherein a created bundle of emails comprises: a grouping of two or more emails, a categorization for the grouping of emails and an identification tag associated with the categorization.
 3. The method of claim 2, wherein the created bundles of emails comprise one or more of: user-created bundles of emails and auto-generated bundles of emails for the user account.
 4. The method of claim 2, wherein the user actions comprise a user action of moving an email from a first created bundle to a second created bundle.
 5. The method of claim 2, further comprising: generating, based on an application of the bundle generation model, a suggestion for re-organizing created bundles of emails in the mailbox of the user account and surfacing the suggestion in association with the mailbox of the user account.
 6. The method of claim 1, wherein the server side metric analysis evaluates data that comprises: sender domains for emails received by the user account, telemetry data corresponding with user access actions for specific emails, user rules set in association with the user account and telemetry data from cross-application usage by the user account for a suite of platform applications.
 7. The method of claim 1, further comprising: generating a notification for automatic bundling of the bundle of emails, and transmitting the notification to the user account.
 8. A system comprising: at least one processor; and a memory operatively connected with the at least one processor storing computer-executable instructions that, when executed by the at least one processor, causes the at least one processor to execute a method that comprises: accessing email data associated with a user account of an email service, evaluating the email data by applying a bundle generation model that evaluates the emails for bundling associations based on: user signal data from actions pertaining to categorization of specific emails, content and metadata corresponding with the email data, and server side metric analysis of activity corresponding with the user account, automatically bundling two or more emails into a bundle of emails based on an evaluation result from application of the bundle generation model, and transmitting the bundle of emails for display in a mailbox of the user account.
 9. The system of claim 8, wherein the user signal data pertains to user actions that correspond with created bundles of emails in the mailbox of the user account, and wherein a created bundle of emails comprises: a grouping of two or more emails, a categorization for the grouping of emails and an identification tag associated with the categorization.
 10. The system of claim 9, wherein the created bundles of emails comprise one or more of: user-created bundles of emails and auto-generated bundles of emails for the user account.
 11. The system of claim 9, wherein the user actions comprise a user action of moving an email from a first created bundle to a second created bundle.
 12. The system of claim 9, wherein the method, executed by the at least one processor, further comprises: generating, based on an application of the bundle generation model, a suggestion for re-organizing created bundles of emails in the mailbox of the user account and surfacing the suggestion in association with the mailbox of the user account.
 13. The system of claim 8, wherein the server side metric analysis evaluates data that comprises: sender domains for emails received by the user account, telemetry data corresponding with user access actions for specific emails, user rules set in association with the user account and telemetry data from cross-application usage by the user account for a suite of platform applications.
 14. The system of claim 8, wherein the method, executed by the at least one processor, further comprises: generating a notification for automatic bundling of the bundle of emails, and transmitting the notification to the user account.
 15. A computer-readable medium storing computer-executable instructions that, when executed by at least one processor, causes the at least one processor to execute a method comprising: accessing email data associated with a user account of an email service; evaluating the email data by applying a bundle generation model that evaluates the emails for bundling associations based on: user signal data from actions pertaining to categorization of specific emails, content and metadata corresponding with the email data, and server side metric analysis of activity corresponding with the user account; automatically bundling two or more emails into a bundle of emails based on an evaluation result from application of the bundle generation model; and transmitting the bundle of emails for display in a mailbox of the user account.
 16. The computer-readable medium of claim 15, wherein the user signal data pertains to user actions that correspond with created bundles of emails in the mailbox of the user account, wherein a created bundle of emails comprises: a grouping of two or more emails, a categorization for the grouping of emails and an identification tag associated with the categorization, and wherein the created bundles of emails comprise one or more of: user-created bundles of emails and auto-generated bundles of emails for the user account.
 17. The computer-readable medium of claim 16, wherein the user actions comprise a user action of moving an email from a first created bundle to a second created bundle.
 18. The computer-readable medium of claim 16, wherein the executed method further comprising: generating, based on an application of the bundle generation model, a suggestion for re-organizing created bundles of emails in the mailbox of the user account and surfacing the suggestion in association with the mailbox of the user account.
 19. The computer-readable medium of claim 15, wherein the server side metric analysis evaluates data that comprises: sender domains for emails received by the user account, telemetry data corresponding with user access actions for specific emails, user rules set in association with the user account and telemetry data from cross-application usage by the user account for a suite of platform applications.
 20. The computer-readable medium of claim 15, wherein the executed method further comprising: generating a notification for automatic bundling of the bundle of emails, and transmitting the notification to the user account. 